Add customizable detail field to request table view cells #115
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thank you for the changes you've made in this PR. It looks good to me and I plan to merge it soon. I think it would be helpful to include an example in the README file to show how the label customization feature can be used. Would you be able to provide a simple code snippet or usage example that we could include in the README? This would help our users understand how to use this feature more easily. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
When using Wormholy in GraphQL projects, it is difficult to oversee the GraphQL operations sent, due to the endpoint being the same in every single case.
Solution:
Add a label to
RequestCellthat can be customized what to show.Example usage:
Screenshot:
(Note our debug menu changes the navigation title, please ignore that).